Script crashes DOORS in 9.1, but not in 8.3

ePiallat - Thu Feb 26 04:34:32 EST 2009
Hi,

My guts tell the issue doesn't come from your script, but from the scanned data:
How do you access the "Last Modified On" attribute?
If it is from "Module", it means while opening modules you fire triggers, DXL attribute computing and perhaps Layout DXL.
If it is from "ModuleProperties" or "Module", you still fire module-level DXL attribute computing.

In any case, can you tell for sure your migrated modules are clean?
Another theory would be a memory leak. Use of "ModuleProperties" seems to have such an issue, but as its behaviour differs from a version to another I can't confirm it with DOORS 9.1 myself.

– Éric

SystemAdmin - Fri Feb 27 10:18:31 EST 2009
Here's the code that is causing the issue:

for itm in current Project do
{
progressStep ++cnt
if (progressCancelled)
{
if (confirm("Halt Progress?"))
{
progressStop
CleanUp
halt
}
}
if (type(itm) == "Project")
{
csvfile << "Project," name(itm) ",,,\n"
}
if (type(itm) == "Folder")
{
csvfile << "Folder," name(itm) ",,,\n"
}
if (type(itm) == "Formal")
{
modN = fullName(itm)
m = read(modN, false)
if (m != null)
{
lastModOn = m."Last Modified On"
lastModBy = m."Last Modified By"
if (existsUser(lastModBy))
{
u = find(lastModBy)
uName = u.fullName
if (uName == null)
{
uName = lastModBy
}
}
else
{
uName = "Unknown User"
}
csvfile << "Formal Module," name(itm) "," lastModOn "," uName ",\n"
}
else
{
csvfile << "ERROR!, Formal Module, Could Not, Be Opened,\n"
cantopen++
}
}
else
{
//No Output
}
}
I'm not sure what you mean by migrated modules being clean. Also, how can I check if triggers are causing this issue?

SystemAdmin - Fri Feb 27 10:51:33 EST 2009
I've isolated the issue to this line:
m = read(modN, false)

I've also added a close(m) after the attribute information was gathered, and it did not fix the issue. Why is this read causing the script to fail even if I'm closing the modules afterwards? Also, is there a way to get attribute information without doing this read?

SystemAdmin - Fri Feb 27 10:51:33 EST 2009
I've isolated the issue to this line:
m = read(modN, false)

I've also added a close(m) after the attribute information was gathered, and it did not fix the issue. Why is this read causing the script to fail even if I'm closing the modules afterwards? Also, is there a way to get attribute information without doing this read?